Skip to main content

Resubmit Application

Overview​

The Resubmit Application API provides functionality for updating existing application records. This endpoint utilizes the identical interface, authentication protocols, and validation rules as the Submit Application API.

Prerequisites: Please review the Submit Application API documentation for comprehensive details regarding authentication, request body structure, field definitions, validation rules, and all other implementation requirements.

Authentication​

This endpoint requires authentication. See API Authentication for detailed requirements and how to obtain credentials.

Endpoint​

PUT /api/applications/submit

Request Body​

Uses the identical request structure as the Submit Application API. Refer to the Submit Application documentation for complete TypeScript interface definitions.

Existing Application Modification (Resubmission)​

Include ID Fields for Updates

When updating existing application records, include the following identifier fields in the request payload:

  • applicationId - Required: Unique identifier of the target application record
  • company._id - Required for company applications: Unique identifier of the existing company record
  • person._id - Required for person applications: Unique identifier of the existing person record

Request Example​

{
"applicationId": "60d5ecb54f3d2b001f8b4568",
"affiliateId": "affiliate123",
"applicationName": "Updated Application Submission",
"person": {
"_id": "60d5ecb54f3d2b001f8b4571",
"firstName": "John",
"lastName": "Doe",
"email": "john.doe.updated@example.com"
}
}

Response Structure​

Successful Application Update​

{
"statusCode": 200,
"message": "Application updated successfully",
"data": {
"applicationId": "60d5ecb54f3d2b001f8b4568",
"status": "pending"
}
}

Usage Guidelines​

  • For Updates: Include the applicationId and the relevant entity ID (company._id or person._id)
  • All other requirements are identical to the Submit Application API